Systems and methods for congestion control in an integrated access and backhaul network

ABSTRACT

An intermediate IAB node may determine whether congestion data satisfies a first threshold and may provide the congestion data to a parent IAB node when the congestion data satisfies the first threshold to cause the parent IAB node to apply local congestion control.

BACKGROUND

A mobile network may include a wireless backhaul network, sometimesreferred to as an integrated access and backhaul (IAB) network. In anIAB network, at least one base station acts as an anchor base station(also referred to as an IAB donor) that communicates with a core network(via a wired backhaul link). The IAB network may include one or morenon-anchor base stations (also referred to as IAB nodes), that maycommunicate directly with or indirectly with (for example, via one ormore other non-anchor base stations) the anchor base station via one ormore wireless backhaul links to form a backhaul path to the corenetwork.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1J are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a flow chart of an example process relating to congestioncontrol in an IAB network.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

As the reliance on wireless communications becomes more widespread, andas more user equipment demand access to mobile networks, managing andcontrolling network traffic becomes increasingly important. Suchincreases in network traffic call for more effective ways to monitor,control, and alleviate network congestion in a mobile network. Networkcongestion can occur when a base station associated with a coverage areasimultaneously supporting multiple connections with multiple userequipment is at or beyond a load capacity of the base station.

In an IAB network, a donor IAB node may use a network controller todetect network congestion via an end-to-end (E2E) feedback loop formedwith an access IAB node (e.g., a child IAB node), and may engage acorrective measure (e.g., a throttling technique, a buffering technique,blocking technique, and/or the like) that deliberately restricts certainnetwork traffic in an attempt to alleviate network congestion at theaccess IAB node.

However, network congestion may occur at an intermediate IAB nodewirelessly connected between the child IAB node and a parent IAB nodethat is wirelessly connected to the donor IAB node. Network congestionmay occur at the intermediate IAB node independent of network congestionoccurring at the IAB child node (e.g., network congestion may not occurat the child IAB node at a time when network congestion occurs at theintermediate IAB node). Because the donor IAB node detects networkcongestion via the E2E feedback loop formed with the child IAB node, thedonor IAB node may not be able to detect network congestion occurring atthe intermediate IAB node.

The congestion at the intermediate IAB node may cause the intermediateIAB node to drop packets and/or to delay the transmission of packets.The dropping of packets and/or delaying the transmission of packets mayrequire the packets to be re-transmitted thereby causing additionalcomputing resources (e.g., processor resources, memory resources,communication resources, and/or the like) to be utilized.

Some implementations described herein provide systems and methods fordetecting and correcting network congestion occurring at an intermediateIAB node. The intermediate IAB node may perform a tiered approach tocontrolling network congestion at the intermediate IAB node. Based onthe level of network congestion experienced and/or an amount of time forwhich the network congestion is experienced, the intermediate IAB nodemay cause one or more measures for reducing the network congestion to beperformed.

The intermediate IAB node may compare congestion data associated withthe intermediate IAB and a corresponding load threshold to determinewhether network congestion exists at the intermediate IAB node. Theintermediate IAB node may perform a first corrective action based ondetermining that the congestion data satisfies a first threshold for afirst amount of time. The first corrective action may be a local controlmeasure designed to alleviate traffic at the intermediate IAB node. Insome instances (e.g., if the first corrective action is inadequate toalleviate traffic at the intermediate IAB node), the congestion data maysatisfy a second load threshold for a second amount of time. Theintermediate IAB node may perform a second corrective action (e.g.,different from the first corrective action) designed to alleviatecongestion at the intermediate IAB node. In some instances (e.g., if thefirst and second corrective actions are inadequate to alleviate trafficat the intermediate IAB node), the congestion data may satisfy a thirdload threshold for a third amount of time. The intermediate IAB node mayperform a third corrective action (e.g., different from the first andsecond corrective actions) designed to alleviate congestion at theintermediate IAB node.

In this way, the systems and methods described herein minimize theoccurrence of congestion within an IAB network, reduce downtime causedby network congestion, and help maintain network devices of the IABnetwork operating in optimal conditions. Furthermore, the systems andmethods described herein enable user equipment, application networkdevices, and/or other devices connected via the IAB network to maintainconnections to the IAB network. Moreover, end user devices experiencefewer signal degradations, fewer signal losses, less latency, andoverall better connection quality. Also, the systems and methodsdescribed herein provide automated processes related to detecting andcontrolling network congestion, which helps to conserve computationaland network resources (e.g., processing resources, memory resources,power resources, communication resources, and/or the like) that mayotherwise be used to detect and control network traffic.

FIGS. 1A-1J are diagrams of one or more examples implementations 100described herein. As shown in FIGS. 1A-1J, the example implementation(s)100 may include an IAB network including a donor IAB node 110-1, aparent IAB node 110-2, an intermediate IAB node 110-3, a child IAB node110-4, and user equipment (UE) 105 (e.g., UE 105-1 through UE 105-4, asshown in FIG. 1A). The child IAB node 110-4, the parent IAB node 110-2,and/or the donor IAB node 110-1 may perform one or more functions tocontrol network congestion occurring at the intermediate IAB node 110-3,as described below.

As shown in FIGS. 1A-1J, a network includes a wireless backhaul network,sometimes referred to as an integrated access and backhaul (IAB) networkthat includes a plurality of IAB nodes 110 that communicate with one ormore UE 105 via one or more access communication links.

The donor IAB node 110-1 may be an anchor base station that communicateswith a core network 115 via a wired or optical backhaul link, such as afiber connection. As shown in FIG. 1A, the donor IAB node 110-1 isconnected to the parent IAB node 110-2. For example, the donor IAB node110-1 may be connected to the parent IAB node 110-2 via an F1 interfaceor any other wireless interface.

The parent IAB node 110-2, the intermediate IAB node 110-3, and thechild IAB node 110-4 may be non-anchor base stations that communicatedirectly, or indirectly (e.g., via one or more other non-anchor basestations), with the anchor base station (e.g., donor IAB node 110-1) viaone or more wireless backhaul links to form a backhaul path to the corenetwork for carrying backhaul traffic. As shown in FIG. 1A, theintermediate IAB node 110-3 may be connected between the parent IAB node110-2 and the child IAB node 110-4. For example, the intermediate IABnode 110-3 may be connected to the parent IAB node 110-2 and the childIAB node 110-4 via respective interfaces such as an F1 interface.

In some implementations, the intermediate IAB node 110-3 may detectnetwork congestion at the intermediate IAB node 110-3. For example, theintermediate IAB node 110-3 may detect network congestion at theintermediate IAB node 110-3 based on congestion data associated with theintermediate IAB node. The congestion data may include informationrelating to a load level of the intermediate IAB node 110-3 over aparticular time. For example, congestion data may include a number ofunique user equipment simultaneously connected to the intermediate IABnode 110-3, a number of unique Radio Resource Control (RRC) connections,a number of Physical Resource Blocks (PRBs) in use, and/or anotherindication of the load level of the intermediate IAB node 110-3 atdifferent points in time over the particular period of time.

In some implementations, the congestion data may be provided as a ratiobetween a number of connections in use and a number of availableconnections, a percentage of connections in use, and/or anotherindication of the capacity of the intermediate IAB node 110-3. In someimplementations, the congestion data may be provided in relation to acapacity limit of the intermediate IAB node 110-3.

In some implementations, the intermediate IAB node 110-3 determines thecongestion data based on monitoring traffic transmitted to and/or fromthe intermediate IAB node 110-3. Alternatively, and/or additionally, theintermediate IAB node 110-3 receives the congestion data from anotherdevice (e.g., donor IAB node 110-1, parent IAB node 110-2, and/or thelike). The intermediate IAB node 110-3 may store the congestion data ina data structure (e.g., a database, a list, a table, and/or the like)accessible by the intermediate IAB node 110-3, and may update thecongestion data periodically, intermittently, or continuously inreal-time.

As shown in FIG. 1B, and by reference number 120, the intermediate IABnode 110-3 determines whether congestion data satisfies a firstthreshold for more than a first time period. The congestion data mayinclude information relating to a load level of the intermediate IABnode 110-3 at particular points of time over a particular time (e.g.,every second, every minute, every hour, and/or the like). In someimplementations, the intermediate IAB node 110-3 compares the congestiondata determined at multiple points in time and a first threshold anddetermines whether network congestion is occurring at the intermediateIAB node 110-3 for more than the first time period based on thecomparison.

The first threshold may be defined in terms of a number of unique userequipment simultaneously connected to the coverage area, a number ofunique RRC connections, a number of PRBs in use, a ratio between anumber of connections in use and a number of available connections, apercentage of connections in use, and/or another indication of the loadthreshold. For example, the first threshold may be defined based on acapacity limit of the intermediate IAB node 110-3 (e.g., approximately80% of the capacity limit of the intermediate IAB node 110-3,approximately 95% of the capacity limit of the intermediate IAB node110-3, and/or the like).

In some implementations, the intermediate IAB node 110-3 determines thatthe congestion data does not satisfy the first threshold. For example,the intermediate IAB node 110-3 may determine that a capacity of theintermediate IAB node 110-3 was less than 80% of the capacity limit ofthe intermediate IAB node 110-3 for an entire period of time relating tothe congestion data.

In some implementations, the intermediate IAB node 110-3 determines thatone or more points of congestion data satisfy the first threshold butthat the congestion data does not satisfy the first threshold for thefirst time period. For example, the first time period may be about oneminute. The intermediate IAB node 110-3 may determine that the capacityof the intermediate IAB node 110-3 fails to be over 80% of the capacitylimit of the intermediate IAB node 110-3 for at least about one minute.

As shown by reference number 125, the intermediate IAB node 110-3disables local congestion feedback and control when the congestion failsto satisfy the first threshold. Disabling the local congestion feedbackand control may prevent the intermediate IAB node 110-3 from providingcongestion feedback information to the parent IAB node 110-2. In thisway, the intermediate IAB node 110-3 may reduce an amount of congestionfeedback information being transmitted to the parent IAB node 110-2.Reducing the amount of congestion feedback information may conservecomputing resources that may otherwise be used to process congestionfeedback information indicating that the intermediate IAB node 110-3 isnot currently experiencing congestion at the intermediate IAB node110-3.

In some implementations, the intermediate IAB node 110-3 determines thatthe congestion data satisfies the first threshold for more than thefirst period of time. The first threshold and/or the first time periodmay be configured to correspond to network congestion caused bytransient conditions experienced by the intermediate IAB node 110-3,such as an intermittent spike in network traffic caused by a largenumber of UE 105 s traveling through a coverage area of the intermediateIAB node 110-3. As shown in FIG. 1C, and by reference number 130, theintermediate IAB node 110-3 provides the congestion data to the parentIAB node 110-2 over a backhaul adaption protocol (BAP) layer when thecongestion data satisfies the first threshold for more than the firstperiod of time.

The parent IAB node 110-2 may receive the congestion data via the BAPlayer. The parent IAB node 110-2 may analyze the congestion data anddetermine that the network congestion at the intermediate IAB node 110-3and may identify one or more local congestion control measures to beapplied to alleviate the network congestion at the intermediate IAB node110-3.

As shown in FIG. 1D, and by reference number 135, the intermediate IABnode 110-3 applies local congestion control with the parent IAB node110-2 based on the congestion data satisfying the first threshold formore than the first period of time. In some implementations, the localcongestion control measures include scheduling additional resources forthe intermediate IAB node 110-3. For example, the parent IAB node 110-2may schedule additional uplink resources, additional downlink resources,and/or the like for the intermediate IAB node 110-3 to alleviate thenetwork congestion at the intermediate IAB node 110-3.

The intermediate IAB node 110-3 may determine whether the localcongestion control measures alleviated the network congestion at theintermediate IAB node 110-3. The intermediate IAB node 110-3 may obtaincongestion data for a period of time occurring after the localcongestion control measures have been applied. As shown in FIG. 1E, andby reference number 140, the intermediate IAB node 110-3 determineswhether the congestion data satisfies a second threshold for more than asecond time period.

In some implementations, the second threshold includes (e.g., is greaterthan) the first threshold. For example, the first threshold may be 80%of the capacity limit of the intermediate IAB node 110-3 and the secondthreshold may be 90% of the capacity limit of the intermediate IAB node110-3.

In some implementations, the second threshold is the same as the firstthreshold and the intermediate IAB node 110-3 determines whether thecongestion data continues to satisfy the first threshold for anadditional period of time. For example, the intermediate IAB node 110-3may determine whether the local congestion control measures have beeneffective in reducing the network congestion at the intermediate IABnode 110-3 (e.g., whether the intermediate IAB node 110-3 is continuingto remain at a capacity level over 80% of a capacity of the intermediateIAB node 110-3).

In some implementations, the intermediate IAB node 110-3 determines thatthe congestion data fails to satisfy the second threshold for the secondperiod of time. For example, the intermediate IAB node 110-3 maydetermine, based on the congestion data, that applying the local controlmeasures has resulted in a reduction in the network congestion at theintermediate IAB node 110-3. As shown by reference number 145, theintermediate IAB node 110-3 disables user plane intermediate IAB nodecongestion feedback when the congestion data fails to satisfy the secondthreshold.

Disabling the user plane intermediate IAB node congestion feedback mayprevent the intermediate IAB node 110-3 from providing congestionfeedback information to the donor IAB node 110-1. In this way, theintermediate IAB node 110-3 may reduce an amount of congestion feedbackinformation being transmitted to the donor IAB node 110-1. Reducing theamount of congestion feedback information may conserve computingresources that may otherwise be used to process congestion feedbackinformation indicating that the intermediate IAB node 110-3 is notcurrently experiencing congestion at the intermediate IAB node 110-3.

In some implementations, the congestion data may continue to satisfy thefirst threshold for a subsequent first time period. The intermediate IABnode 110-3 may transmit congestion control data to the parent IAB node110-2 over the BAP layer and the intermediate IAB node 110-3 may applylocal congestion control measure with the parent IAB node 110-2, in amanner similar to that described above with respect to FIGS. 1C and 1D.

In some implementations, the intermediate IAB node 110-3 determines thatthe congestion data satisfies the second threshold for more than thesecond time period. As shown in FIG. 1F, and by reference number 150,the intermediate IAB node 110-3 provides the congestion data to thedonor IAB node 110-1 via a user plane when the congestion data satisfiesthe second threshold for more than the second time period. Theintermediate IAB node 110-3 may provide the congestion data to the donorIAB node 110-1 via the parent IAB node 110-2 over an F1-U interface.

The donor IAB node 110-1 may receive the congestion data from theintermediate IAB node 110-3 and may determine to apply user plane flowcontrol to alleviate the network congestion at the intermediate IAB node110-3. In some implementations, the donor IAB node 110-1 may determineto apply user plane flow control based on the congestion data and basedon congestion data received from the child IAB node 110-4. The child IABnode 110-4 may provide congestion data to the donor IAB node 110-1 viaan E2E feedback loop.

As shown in FIG. 1G, and by reference number 155, the donor IAB node110-1 applies user plane flow control based on the congestion datasatisfying the second threshold for more than the second time period.For example, the donor IAB node 110-1 may apply user plane flow controlby allocating or scheduling additional resources for the intermediateIAB node 110-3, by causing the intermediate IAB node 110-3 to transmitdata via an alternate path (e.g., the intermediate IAB node may be adual-mode node that can transmit data via the IAB network and anothernetwork (e.g., a 4G network)), and/or the like.

The intermediate IAB node 110-3 may determine whether applying the userplane flow control alleviated the network congestion at the intermediateIAB node 110-3. The intermediate IAB node 110-3 may obtain congestiondata for a period of time occurring after the user plane flow controlhas been applied. As shown in FIG. 1H, and by reference number 160, theintermediate IAB node 110-3 determines whether the congestion datasatisfies a third threshold for more than a third time period.

In some implementations, the third threshold includes (e.g., is greaterthan) the first threshold and/or the second threshold. For example, thefirst threshold may be 80% of the capacity limit of the intermediate IABnode 110-3, the second threshold may be 90% of the capacity limit of theintermediate IAB node 110-3, and the third threshold may be 95% of thecapacity limit of the intermediate IAB node 110-3.

In some implementations, the third threshold is the same as the firstthreshold and/or the second threshold and the intermediate IAB node110-3 determines whether the congestion data continues to satisfy thefirst threshold and/or the second threshold for an additional period oftime. For example, the intermediate IAB node 110-3 may determine whetherthe local congestion control measures and or the user plane flow controlhave been effective in reducing the network congestion at theintermediate IAB node 110-3 (e.g., whether the intermediate IAB node110-3 is continuing to remain at a capacity level over 80% of a capacityof the intermediate IAB node 110-3).

In some implementations, the intermediate IAB node 110-3 determines thatthe congestion data fails to satisfy the third threshold for the thirdperiod of time. For example, the intermediate IAB node 110-3 maydetermine, based on the congestion data, that applying the user planeflow control has resulted in a reduction in the network congestion atthe intermediate IAB node 110-3. As shown by reference number 165, theintermediate IAB node 110-3 disables control plane intermediate IAB nodecongestion feedback when the congestion data fails to satisfy the thirdthreshold.

Disabling the control plane intermediate IAB node congestion feedbackmay prevent the intermediate IAB node 110-3 from providing congestionfeedback information to the donor IAB node 110-1 via the control plane.In this way, the intermediate IAB node 110-3 may reduce an amount ofdata being transmitted to the donor IAB node 110-1 via the control planethereby conserving computing resources that would otherwise be utilizedto process the data.

In some implementations, the congestion data may continue to satisfy thefirst threshold for a subsequent first time period. The intermediate IABnode 110-3 may transmit congestion control data to the parent IAB node110-2 over the BAP layer and the intermediate IAB node 110-3 may applylocal congestion control measure with the parent IAB node 110-2, in amanner similar to that described above with respect to FIGS. 1C and 1D.

In some implementations, the congestion data may continue to satisfy thesecond threshold for a subsequent second time period. The intermediateIAB node 110-3 may transmit congestion control data to the donor IABnode 110-1 via the user plane and the donor IAB node 110-1 may userplane flow control, in a manner similar to that described above withrespect to FIGS. 1F and 1G.

In some implementations, the intermediate IAB node 110-3 determines thatthe congestion data satisfies the third threshold for more than thethird time period. As shown in FIG. 1I, and by reference number 170, theintermediate IAB node 110-3 provides the congestion data to the donorIAB node 110-1 via a control plane when the congestion data satisfiesthe third threshold form more than the third time period. Theintermediate IAB node 110-3 may provide the congestion data to the donorIAB node 110-1 over an FI-C interface.

The donor IAB node 110-1 may receive the congestion data from theintermediate IAB node 110-3 via the control plane and may determine toapply control plane flow control to alleviate the network congestion atthe intermediate IAB node 110-3. In some implementations, the donor IABnode 110-1 may determine to apply control plane flow control based onthe congestion data and based on congestion data received from the childIAB node 110-4. The child IAB node 110-4 may provide congestion data tothe donor IAB node 110-1 via an E2E feedback loop.

As shown in FIG. 1J, and by reference number 175, the donor IAB node110-1 applies control plane flow control based on the congestion datasatisfying the third threshold for more than the third time period. Insome implementations, the donor IAB node 110-1 may apply control planeflow control by performing re-routing (e.g., if alternative routes existwith sufficient capacity), applying topology adaptation usingalternative links, and/or the like.

For example, the donor IAB node 110-1 may determine that the child IABnode 110-4 is able to establish a wireless communication link withanother IAB node (intermediate IAB node 110-5, as shown in FIG. 1J). Thedonor IAB node 110-1 may cause the child IAB node 110-4 to transmit datavia the other IAB node rather than to the intermediate IAB node 110-3.

By utilizing a feedback loop which extends between the donor IAB node110-1 and the intermediate IAB node 110-3, the donor IAB node 110-1 maymonitor and control network congestion occurring at the intermediate IABnode 110-3 more effectively relative to other systems for monitoring andcontrolling network traffic at intermediate IAB nodes. Furthermore, byutilizing a three-tier approach to controlling network congestion at anintermediate IAB node, the intermediate IAB node 110-3 and/or the parentIAB node 110-2 is able to initiate corrective actions at theintermediate IAB node 110-3 earlier and avoid congestion events.

As indicated above, FIGS. 1A-1J are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 1A-1J.The number and arrangement of devices shown in FIGS. 1A-1J are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged than those shown inFIGS. 1A-1J. Furthermore, two or more devices shown in FIGS. 1A-1J maybe implemented within a single device, or a single device shown in FIGS.1A-1J may be implemented as multiple, distributed devices. Additionally,or alternatively, a set of devices (e.g., one or more devices) shown inFIGS. 1A-1J may perform one or more functions described as beingperformed by another set of devices shown in FIGS. 1A-1J.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,example environment 200 may include UE 105, IAB 110, core network 115,and a data network 255. Devices and/or networks of example environment200 may interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 105 includes one or more devices capable of receiving, generating,storing, processing, and/or providing information, such as informationdescribed herein. For example, UE 105 can include a mobile phone (e.g.,a smart phone, a radiotelephone, and/or the like), a laptop computer, atablet computer, a desktop computer, a handheld computer, a gamingdevice, a wearable communication device (e.g., a smart watch, a pair ofsmart glasses, and/or the like), a mobile hotspot device, a fixedwireless access device, customer premises equipment, an autonomousvehicle, or a similar type of device.

IAB 110 includes one or more devices for providing IAB functionality todevices connected to IAB 110. In some implementations, IAB 110 is ananchor node (e.g., IAB donor node) that connects to a core network via awired connection. In these implementations, IAB 110 may connect to oneor more devices of the core network that provide a core access andmobility management function. For example, an Ng interface of an anchornode may terminate at a core network. Additionally, or alternatively,IAB 110 may connect to one or more devices of the core network thatprovide a core access and mobility management function (e.g., AMF). Insome implementations, IAB 110 includes a base station, such as an anchorbase station.

In some implementations, IAB 110 is a non-anchor node (e.g., a parentIAB node, an intermediate IAB node, a child IAB node, and/or the like).In these implementations, IAB 110 may include mobile terminal (MT)functions (also sometimes referred to as UE functions (UEF)) anddistributed unit (DU) functions (also sometimes referred to as accessnode functions (ANF)). The MT functions may be controlled and/orscheduled by another non-anchor node and/or an anchor node. The DUfunctions may control and/or schedule other non-anchor nodes and/or UEs105.

In some implementations, core network 115 may include an examplefunctional architecture in which systems and/or methods described hereinmay be implemented. For example, core network 115 may include an examplearchitecture of a fifth generation (5G) next generation (NG) corenetwork included in a 5G wireless telecommunications system. While theexample architecture of core network 115 shown in FIG. 2 may be anexample of a service-based architecture, in some implementations, corenetwork 115 may be implemented as a reference-point architecture, a 4Gcore network, and/or the like.

As shown in FIG. 2, core network 115 may include a number of functionalelements. The functional elements may include, for example, a networkslice selection function (NSSF) 205, a network exposure function (NEF)210, an authentication server function (AUSF) 215, a unified datamanagement (UDM) component 220, a policy control function (PCF) 225, anapplication function (AF) 230, an access and mobility managementfunction (AMF) 235, a session management function (SMF) 240, a userplane function (UPF) 245, and/or the like. These functional elements maybe communicatively connected via a message bus 250. Each of thefunctional elements shown in FIG. 2 is implemented on one or moredevices associated with a wireless telecommunications system. In someimplementations, one or more of the functional elements may beimplemented on physical devices, such as an access point, a basestation, a gateway, and/or the like. In some implementations, one ormore of the functional elements may be implemented on a computing deviceof a cloud computing environment.

NSSF 205 includes one or more devices that select network sliceinstances for UE 105. By providing network slicing, NSSF 205 allows anoperator to deploy multiple substantially independent end-to-endnetworks potentially with the same infrastructure. In someimplementations, each slice may be customized for different services.

NEF 210 includes one or more devices that support exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services.

AUSF 215 includes one or more devices that act as an authenticationserver and support the process of authenticating UE 105 in the wirelesstelecommunications system.

UDM 220 includes one or more devices that store user data and profilesin the wireless telecommunications system. UDM 220 may be used for fixedaccess, mobile access, and/or the like, in core network 115.

PCF 225 includes one or more devices that provide a policy frameworkthat incorporates network slicing, roaming, packet processing, mobilitymanagement, and/or the like.

AF 230 includes one or more devices that support application influenceon traffic routing, access to NEF 210, policy control, and/or the like.

AMF 235 includes one or more devices that act as a termination point fornon-access stratum (NAS) signaling, mobility management, and/or thelike.

SMF 240 includes one or more devices that support the establishment,modification, and release of communication sessions in the wirelesstelecommunications system. For example, SMF 240 may configure trafficsteering policies at UPF 245, enforce user equipment IP addressallocation and policies, and/or the like.

UPF 245 includes one or more devices that serve as an anchor point forintraRAT and/or interRAT mobility. UPF 245 may apply rules to packets,such as rules pertaining to packet routing, traffic reporting, handlinguser plane QoS, and/or the like.

Message bus 250 represents a communication structure for communicationamong the functional elements. In other words, message bus 250 maypermit communication between two or more functional elements.

Data network 255 includes one or more wired and/or wireless datanetworks. For example, data network 255 may include an IP MultimediaSubsystem (IMS), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a private network such as a corporate intranet, an ad hocnetwork, the Internet, a fiber optic-based network, a cloud computingnetwork, a third party services network, an operator services network,and/or the like, and/or a combination of these or other types ofnetworks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of exampleenvironment 200 may perform one or more functions described as beingperformed by another set of devices of example environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to UE 105, a base station of IAB 110, NSSF 205, NEF 210,AUSF 215, UDM 220, PCF 225, AF 230, AMF 235, SMF 240, and/or UPF 245. Insome implementations, UE 105, the base station of IAB 110, NSSF 205, NEF210, AUSF 215, UDM 220, PCF 225, AF 230, AMF 235, SMF 240, and/or UPF245 may include one or more devices 300 and/or one or more components ofdevice 300. As shown in FIG. 3, device 300 may include a bus 310, aprocessor 320, a memory 330, a storage component 340, an input component350, an output component 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more LEDs).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, an RF interface, a universal serial bus (USB)interface, a wireless local area interface, a cellular networkinterface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 associated with systemsand methods for congestion control in IAB networks. In someimplementations, one or more process blocks of FIG. 4 may be performedby an intermediate IAB node (e.g., intermediate IAB node 110-3). In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including theintermediate IAB node, such as donor IAB node 110-1, parent IAB node110-2, child IAB node 110-4, and/or the like. Additionally, oralternatively, one or more process blocks of FIG. 4 may be performed byone or more components of a device 300, such as processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370, and/or the like.

As shown in FIG. 4, process 400 may include determining whethercongestion data, associated with the intermediate IAB node, satisfies afirst threshold for more than a first time period (block 410). Forexample, the intermediate IAB node may determine, backhaul (IAB) node,whether congestion data, associated with the intermediate IAB node,satisfies a first threshold for more than a first time period, asdescribed above.

In some implementations, process 400 may include receiving thecongestion data based on interactions by the intermediate IAB node withone or more user equipment, the child IAB node, or the parent IAB node.

As further shown in FIG. 4, process 400 may include providing thecongestion data to a parent IAB node when the congestion data satisfiesthe first threshold for more than the first time period (block 420). Forexample, the intermediate IAB node may provide the congestion data to aparent IAB node when the congestion data satisfies the first thresholdfor more than the first time period, as described above. In someimplementations, providing the congestion data causes the parent IABnode to apply local congestion control at the intermediate IAB node.

The congestion data may be provided to the parent IAB node over abackhaul adaptation protocol layer when the congestion data satisfiesthe first threshold for more than the first time period.

Process 400 may include disabling local congestion feedback and controlwhen the congestion data fails to satisfy the first threshold.

As further shown in FIG. 4, process 400 may include determining whetherthe congestion data satisfies a second threshold for more than a secondtime period (block 430). For example, the intermediate IAB node maydetermine whether the congestion data satisfies a second threshold formore than a second time period, as described above.

As further shown in FIG. 4, process 400 may include providing thecongestion data to a donor IAB node via a user plane when the congestiondata satisfies the second threshold for more than the second time period(block 440). For example, the intermediate IAB node may provide thecongestion data to a donor IAB node via a user plane when the congestiondata satisfies the second threshold for more than the second timeperiod, as described above. In some implementations, providing thecongestion data to the donor IAB node via the user plane causes thedonor IAB node to apply user plane flow control based on the congestiondata provided to the donor IAB node via the user plane and based onother congestion data provided to the donor IAB node by a child IAB nodeconnected to the intermediate IAB node.

In some implementations, the donor IAB node may be connected to a wiredbackhaul network and the congestion data may be provided to the donorIAB node over an F1 user plane interface.

Process 400 may include disabling user plane congestion feedback whenthe congestion data fails to satisfy the second threshold.

As further shown in FIG. 4, process 400 may include determining whetherthe congestion data satisfies a third threshold for more than a thirdtime period (block 450). For example, the intermediate IAB node maydetermine whether the congestion data satisfies a third threshold formore than a third time period, as described above.

As further shown in FIG. 4, process 400 may include providing thecongestion data to the donor IAB node via a control plane when thecongestion data satisfies the third threshold for more than the thirdtime period (block 460). For example, the intermediate IAB node mayprovide the congestion data to the donor IAB node via a control planewhen the congestion data satisfies the third threshold for more than thethird time period, as described above. In some implementations,providing the congestion data to the donor IAB node via the controlplane causes the donor IAB node to perform control plane flow controlbased on the congestion data provided to the donor IAB node via thecontrol plane and based on the other congestion data provided to thedonor IAB node by the child IAB node.

In some implementations, the congestion data may be provided to thedonor IAB node over an F1 control plane interface.

The local congestion control, the user plane flow control, and thecontrol plane flow control may reduce congestion associated with theintermediate IAB node.

Process 400 may include disabling control plane congestion feedback whenthe congestion data fails to satisfy the third threshold.

In some implementations, process 400 may include using alternate linksto transmit data based on the donor IAB node applying the control planeflow control.

Process 400 may include providing feedback traffic upstream to theparent IAB node and providing the feedback traffic downstream to thechild IAB node.

In some implementations, the intermediate IAB node, the parent IAB node,and the donor IAB node each include a gNodeB.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc., depending on the context.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: determining, by an intermediate integrated access and backhaul (IAB) node, whether congestion data, associated with the intermediate IAB node, satisfies a first threshold; providing, by the intermediate IAB node, the congestion data to a parent IAB node when the congestion data satisfies the first threshold, wherein providing the congestion data causes the parent IAB node to apply local congestion control at the intermediate IAB node.
 2. The method of claim 1, further comprising: determining, by the intermediate IAB node, whether the congestion data satisfies a second threshold; and providing, by the intermediate IAB node, the congestion data to a donor IAB node via a user plane when the congestion data satisfies the second threshold, wherein providing the congestion data to the donor IAB node via the user plane causes the donor IAB node to apply user plane flow control based on the congestion data provided to the donor IAB node via the user plane and based on other congestion data provided to the donor IAB node by a child IAB node connected to the intermediate IAB node.
 3. The method of claim 1, further comprising: disabling local congestion feedback and control when the congestion data fails to satisfy the first threshold.
 4. The method of claim 2, further comprising: disabling user plane congestion feedback when the congestion data fails to satisfy the second threshold.
 5. The method of claim 1, further comprising: determining, by the intermediate IAB node, whether the congestion data satisfies a third threshold; and providing, by the intermediate IAB node, the congestion data to the donor IAB node via a control plane when the congestion data satisfies the third threshold, wherein providing the congestion data to the donor IAB node via the control plane causes the donor IAB node to perform control plane flow control based on the congestion data provided to the donor IAB node via the control plane and based on the other congestion data provided to the donor IAB node by a child IAB node connected to the intermediate IAB node.
 6. The method of claim 5, further comprising: using alternate links to transmit data based on the donor IAB node applying the control plane flow control.
 7. The method of claim 5, further comprising: disabling control plane congestion feedback when the congestion data fails to satisfy the third threshold.
 8. An intermediate integrated access and backhaul (IAB) node, comprising: one or more processors configured to: determine whether congestion data, associated with the intermediate IAB node, satisfies a first threshold; selectively: disable local congestion feedback and control when the congestion data fails to satisfy the first threshold, or provide the congestion data to a first non-anchor IAB node when the congestion data satisfies the first threshold, wherein providing the congestion data to the first non-anchor IAB node causes the first non-anchor IAB node to apply local congestion control based on the congestion data; determine whether the congestion data satisfies a second threshold; and selectively: disable user plane congestion feedback when the congestion data fails to satisfy the second threshold, or provide the congestion data to an anchor IAB node via a user plane when the congestion data satisfies the second threshold, wherein providing the congestion data to the anchor IAB node via the user plane causes the anchor IAB node to apply user plane flow control based on the congestion data provided to the anchor IAB node via the user plane and based on other congestion data provided to the anchor IAB node by a second non-anchor IAB node associated with the intermediate IAB node.
 9. The intermediate IAB node of claim 8, wherein the one or more processors are configured further to: determine whether the congestion data satisfies a third threshold; and provide the congestion data to the anchor IAB node via a control plane when the congestion data satisfies the third threshold, wherein providing the congestion data to the anchor IAB node via the control plane causes the anchor IAB node to apply control plane flow control based on the congestion data provided to the anchor IAB node via the control plane and the other congestion data provided to the anchor IAB node by the second non-anchor IAB node.
 10. The intermediate IAB node of claim 9, wherein the one or more processors, when providing the congestion data to the anchor IAB node via the user plane, are configured to: provide the congestion data to the anchor IAB node over an user plane interface; and wherein the one or more processors, when providing the congestion data to the anchor IAB node via the control plane, are configured to: provide the congestion data to the anchor IAB node over a control plane interface.
 11. The intermediate IAB node of claim 8, wherein the one or more processors are further configured to: receive the congestion data based on interactions by the intermediate IAB node with: one or more user equipment, the first non-anchor IAB node, or the second non-anchor IAB node.
 12. The intermediate IAB node of claim 8, wherein the anchor IAB node is connected to a wired backhaul network.
 13. The intermediate IAB node of claim 8, wherein the one or more processors are further configured to: provide feedback traffic upstream to the first non-anchor IAB node; and provide the feedback traffic downstream to the second non-anchor IAB node.
 14. The intermediate IAB node of claim 8, wherein the intermediate IAB node, the first non-anchor IAB node, and the anchor IAB node each include a gNodeB.
 15. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of an intermediate integrated access and backhaul (IAB) node, cause the one or more processors to: determine whether congestion data, associated with the intermediate IAB node satisfies a first threshold; provide the congestion data to a parent IAB node over a backhaul adaptation protocol layer when the congestion data satisfies the first threshold, wherein providing the congestion data to the parent IAB node causes the parent IAB node to apply local congestion control based on the congestion data; determine whether the congestion data satisfies a second threshold; provide the congestion data to a donor IAB node, via a user plane and over a user plane interface, when the congestion data satisfies the second threshold, wherein providing the congestion data to the donor IAB node via the user plane causes the donor IAB node to apply user plane flow control based on the congestion data provided to the donor IAB node via the user plane and based on other congestion data provided by a child IAB node; determine whether the congestion data satisfies a third threshold; and provide the congestion data to the donor IAB node, via a control plane and over a control plane interface, when the congestion data satisfies the third threshold, wherein providing the congestion data to the donor IAB node via the control plane causes the donor IAB node to apply control plane flow control based on the congestion data provided to the donor IAB node via the control plane and based on the other congestion data provided by the child IAB node.
 16. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to one or more of: disable local congestion feedback and control when the congestion data fails to satisfy the first threshold; disable user plane congestion feedback when the congestion data fails to satisfy the second threshold; or disable control plane congestion feedback when the congestion data fails to satisfy the third threshold.
 17. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: use alternate links based on the donor IAB node applying the control plane flow control.
 18. The non-transitory computer-readable medium of claim 15, wherein the user plane interface comprises an F1 user plane interface and the control plane interface comprises an F1 control plane interface.
 19. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: receive the congestion data based on interactions by the intermediate IAB node with: one or more user equipment, the child IAB node, or the parent IAB node.
 20. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: provide feedback traffic upstream to the parent IAB node; and provide the feedback traffic downstream to the child IAB node. 